[server] Increase initial lock duration for wsgc WEB-229 #17387
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
easyCZ
commented
Apr 26, 2023
| try { | ||
| await this.mutex.client().using(["workspace-gc"], 30 * 1000, async (signal) => { | ||
| await this.mutex.client().using(["workspace-gc"], initialLockDuration, async (signal) => { |
There was a problem hiding this comment.
The alternative reasonable value would be the actual frequency at which we plan to run the job. The lock is auto-released once the function completes, so it shouldn't be an issue
There was a problem hiding this comment.
I've actually applied that change, as it makes more sense
|
/unhold |
roboquat
added
deployed: webapp
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
We're observing mike-marcacci/node-redlock#168 in prod instances. The fix is to increase the initial duration, or downgrade to 4.2. Given 4.2 has a different API syntax, and isn't in TypeScript, let's try this fix first.
Related Issue(s)
Fixes #
How to test
Documentation
Preview status
gitpod:summary
Build Options:
Run the build with werft instead of GHA
Run Leeway with
--dont-testPublish Options
Installer Options
Add desired feature flags to the end of the line above, space separated
Preview Environment Options:
If enabled this will build
install/previewIf enabled this will create the environment on GCE infra
Valid options are
all,workspace,webapp,ide,jetbrains,vscode,ssh/hold